Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sockets - Grace #36

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Sockets - Grace #36

wants to merge 1 commit into from

Conversation

gracemshea
Copy link

No description provided.

@msfinnan
Copy link

msfinnan commented Mar 4, 2019

What does the line (!array1 or !array2) do?
I like how you loop through this using the index!
Your code looks great, Grace! I'm curious to learn what line 3 does.

@gracemshea
Copy link
Author

the 3rd line returns false if it’s not empty, essentially

Copy link

@eric-andeen eric-andeen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm Eric. I'll be your volunteer code reviewer. I've been a software developer for about a zillion years. I'll be applying most of the same professional standards to your code as I do in the day job. Some of my comments may seem pedantic, persnickety, or irrelevant to the kinds of exercises you're doing in class, but once you start your internship, you'll get the same kind of feedback I'm giving you here.

Nice clean code. Good job!

def array_equals(array1, array2)
raise NotImplementedError
return true if array1 == nil and array2 == nil
return false if !array1 or !array2

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two lines correctly handle all the cases where one array is nil, but there are two readability/maintainability problems.

First, you use (array1 == nil) on one line and then (!array1) on the next line to mean the same thing. Pick one and be consistent, at least within the method. (!array1) is fine for a small codebase where there are no team members who object to terse code. So, basically, not a real-world team. (array1 == nil) is much clearer.

Second, these two lines look like two independent checks for error conditions, but in reality the second line depends on the first. It's the cleanest way to write the code, but makes it easy for a future maintenance programmer to muck it up. Maybe add a comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants